-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update to support later vscode versions #2
base: main
Are you sure you want to change the base?
Conversation
@NixM0nk3y this is cool - Thanks |
The updated extensions are commited into the develop branch of my testing fork. You should be able to follow the extension rebuild instructions to generate a local vsix to install. |
@NixM0nk3y Thank you for the kick :) |
@NixM0nk3y
Looks like there is more to do - my first time hacking around with node.js seams like fun |
Thank guys. Hope pico-go can be upgrade soon. Otherwise I need to frozen my vscode upgrade.. |
@cpwood ping |
@NixM0nk3y can you please share the vsix file? for any reason I cannot build it by myself. What should I put into program in launch.json? I am starting to play with node...sorry for lame Q |
can you not just build it locally -> then drop |
I've build a unofficial version and published here for folks who don't have a nodejs build environment, should hopefully unblock some pico makers until this extension finds a active maintainer. |
thank-you |
@NixM0nk3y |
Bump modules and the current vscode revision.
Should help resolve https://github.com/cpwood/Pico-Go/issues/122 .
Rebuild the extension and confirmed working on win32 / vscode 1.66.2